VanguardLH wrote on 07.07.2021 15:11
> There are map apps that use OpenStreet (
https://www.openstreetmap.org/)
> map database; however, that is a peer community updating the database,
> so it is inaccurate.
Thank you for adding your point of view to this dicussion as I am learning a
lot from you and from those others who strive to add value to discussions).
We should strive to make a point that all maps are inherently "inaccurate."
Never has a map _ever_ been made which has _not_ been "inaccurate" somehow.
<
https://maps.usgs.gov/map/>
What you mean, most likely is that the Google Maps are more accurate than
OSM maps are. And that's almost certainly true in my humblest of opinions.
But, given _all_ maps are inaccurate - what matters is this question only:
Q: Are they accurate enough?
I've used _every_ free offline map program Vanguard. Every single one.
(I've written about it _many_ times so this is simply empirical evidence.)
In my humblest of opinions, for the areas I drive, the OSM maps are accurate
enough for paved roads (as backcountry is a completely different story.)
<
https://www.usgs.gov/products/maps/topo-maps>
<
https://osmand.net/features/online-maps-plugin>
> Updates depend on someone using an OpenStreet map
> app, and issuing updates, so the user would have to be motivated to
> issue an update, be in a position to send an update (so, like, not when
> they're driving a car), and be accurate. However, most map app users
> are just users, not database maintainers.
True. I've been able to get Google to update their maps, and, in fact, I
wrote about my experience in the past, where, as I recall, it took Google
only about a month to fix the Google Map errors I had provided them.
It all had to be done over the web though as you'll never get them on the
phone (ask me how I know this, and bear in mind, I'm persistent).
I've never even bothered to fix the OSM maps, and, in fact, there's a
certain minor but obvious error in my area that I always zoom into whenever
I'm testing any map program where I can tell, from the existence of that
error, that they're using the OSM maps.
> Osmand is one of those map apps using OpenStreet map data, so I'd
> probably not trust it. I've seen areas, even in cities, that don't get
> updated for many years just because no one using the OpenStreet map app
> bothers to issue updates, and there were changes in those several years
> from the last update.
It's good that you're bringing out your point of view so we can learn.
You are stating facts that I don't think anyone would disagree with.
I think most of us would agree that Google Map accuracy is fantastic.
For you, in the areas you care about, OSM accuracy isn't good enough.
For me, in the areas I care about, OSM accuracy is good enough (for me).
Again, it's good to get your point of view which is different in some ways.
For me, deep in the Santa Cruz Mountains of California, and for me, in the
Silicon Valley and San Francisco Bay Area, the OSM map accuracy, even if it
were truly five years old, is "good enough" accuracy for what I need it for.
Apparently for you, OSM map accuracy is _not_ good enough and that's OK.
Trust me, I know the lack of accuracy on OSM topographical maps, which is
why the use model is important for what you're intending to use OSM maps
for.
For me, I use mostly the ad-free version of MapFactor Navigator, which, as I
recall, uses a variety of map sources (e.g., Tom Tom Maps or OSM maps).
I have the showing of the data selection turned off by default, but you can
select either Tom Tom Commercial Data or OSM Maps upon startup for example.
> I remember when trialing an OpenStreets map app (don't remember the
> name) that it still reported a library was in its old location despite
> the library moved a mile away 3 years before. It showed businesses that
> had closed several years before.
Oh. Now you're talking something else altogether than roadway locations!
Yes. Indeed. The POI database of most of the non-Google maps sucks by way of
comparison to Google Maps' POI. There's absolutely no comparison possible.
That's why I said the address lookup of Google Maps was the cat's meow.
The POI lookup for Google Maps just kills almost _every_ other map database.
There's a _reason_ I said my use model is to use the POI of Google Maps
(either via the web browser shortcut in my maps folder, or Google Maps), and
then I use the coordinates of that lookup result in the offline street maps.
> Yeah, I could've issued updates for
> every inaccuracy that I found, but I wasn't so inclined at the time,
> plus I'd be issuing more updates than in using their map data. And I
> cannot do anything about their delays and inability to have revenue to
> get recent satellite images.
Again, your point of view is useful, and perfectly valid, IMHO.
You'd go nuts trying to update the POI databases of the offline free maps.
There's no doubt that the Google Maps POI database is simply fantastic.
I used to use Garmin's (I had them all over time), and it shocked me that
even the first Google Maps updates were far better than the Garmins were.
It's just amazing how _good_ Google POIs are compared to the others.
> No thanks to community-driven map data. Imagine the chaos with
> community-driven anti-virus software. Those web browser add-ons that
> show site rankings (SiteAdvisor) are worthless, because they rating less
> than 1% of the registered and sited domains, are susceptible to boobs or
> those invested in vendettas against a site, and are out of date (despite
> a site went "good", they are listed as "bad" for many months or years
> later).
Your use model is different than my use model where both have their place.
I aim for privacy. You aim for POI accuracy.
I also aim for backcountry accuracy (where USGS maps are the cat's meow).
<
https://apps.nationalmap.gov/downloader/#/>
For example, I _love_ the historical series of the USGS backcountry maps.
There's a reason different maps serve different people's purposes.
Agree. I don't remember my test conclusion but you won't see it on my phone.
The older versions were not adware. I use the older versions.
They work just fine.
>> 4. Here WeGo
>>
https://play.google.com/store/apps/details?id=com.here.app.maps
>
> Adware (contains ads, but I've not seen any). They have their own map
> data. Not Google map data. Not OpenStreet "community" map data.
>
> <didn't bother to check the rest in your list as to which use whose map
> database, and if adware or not>
Note that I ran an _extensive_ test of _all_ the free offline maps on both
iOS and Android years ago, which we could dig up, but I'm not disagreeing
with your point of view.
If I may summarize your point of view (for you to correct), it's this...
1. Google Maps has an accurate enough road & POI database
2. OSM maps do not have an accurate enough road & POI database
Is that a valid summary of your point of view?
(Please correct where I err as the whole point of Usenet is to learn from
each other and to provide value that everyone else can benefit from.)
Mine is slightly different even as I agree with your Google accuracy POV.
3. Google Maps aren't private enough for me to use except only when needed
4. I use Google Maps for POI lookups mainly (& sometimes for traffic)
5. When I check traffic, I use Google Maps in a web browser instead
6. When I look up POIs, I simply clipboard the coordinates it finds
7. Then I paste those coordinate into any desired offline map program
8. The two I use most are MapFactor Navigator (older ad free versions)
and OSMAnd~ (which is the one on F-Droid mimicking GP OSMAnd+).
For _backcountry_ hiking, it's a completely different story IMHO.
9. Google topo maps suck in my humble opinion, compared to USGS maps.
<
https://store.usgs.gov/map-locator>
10. OSM topo maps also suck, IMHO, compared to the 1:24000 USGS maps.
<
http://www.gmaptool.eu/en/content/usa-osm-topo-routable>
Thank you for adding value to the topic we're discussing on this ng.
--
BTW, I make my own electronic routable backcountry maps when I need to.
I even wrote tutorials on how to make your own electronic routable maps
using Avenza based on instructions provided on the USGS web site.
<
https://www.avenzamaps.com/vendor/3967/usgs-api>
<
https://www.avenzamaps.com/vendor/804/united-states-geological-survey/>
<
https://www.avenzamaps.com/>
<
https://play.google.com/store/apps/details?id=com.Avenza>